Skip to content

ci: setup Java and adb in runner health check (WPB-21881)#4568

Open
emmaoke-w wants to merge 8 commits intodevelopfrom
ci/WPB-21881-runner-health-check-fix
Open

ci: setup Java and adb in runner health check (WPB-21881)#4568
emmaoke-w wants to merge 8 commits intodevelopfrom
ci/WPB-21881-runner-health-check-fix

Conversation

@emmaoke-w
Copy link
Contributor

@emmaoke-w emmaoke-w commented Feb 5, 2026

https://wearezeta.atlassian.net/browse/WPB-21881


PR Submission Checklist for internal contributors

  • The PR Title

    • conforms to the style of semantic commits messages¹ supported in Wire's Github Workflow²
    • contains a reference JIRA issue number like SQPIT-764
    • answers the question: If merged, this PR will: ... ³
  • The PR Description

    • is free of optional paragraphs and you have filled the relevant parts to the best of your ability

What's new in this PR?

  • Fix QA runner health check by setting up Java and adb.

Issues

Briefly describe the issue you have solved or implemented with this pull request. If the PR contains multiple issues, use a bullet list.

Causes (Optional)

Briefly describe the causes behind the issues. This could be helpful to understand the adopted solutions behind some nasty bugs or complex issues.

Solutions

Briefly describe the solutions you have implemented for the issues explained above.

Dependencies (Optional)

If there are some other pull requests related to this one (e.g. new releases of frameworks), specify them here.

Needs releases with:

  • GitHub link to other pull request

Testing

Test Coverage (Optional)

  • I have added automated test to this contribution

How to Test

Briefly describe how this change was tested and if applicable the exact steps taken to verify that it works as expected.

Notes (Optional)

Specify here any other facts that you think are important for this issue.

Attachments (Optional)

Attachments like images, videos, etc. (drag and drop in the text box)


PR Post Submission Checklist for internal contributors (Optional)

  • Wire's Github Workflow has automatically linked the PR to a JIRA issue

PR Post Merge Checklist for internal contributors

  • If any soft of configuration variable was introduced by this PR, it has been added to the relevant documents and the CI jobs have been updated.

References
  1. https://sparkbox.com/foundry/semantic_commit_messages
  2. https://github.com/wireapp/.github#usage
  3. E.g. feat(conversation-list): Sort conversations by most emojis in the title #SQPIT-764.


curl -L -o platform-tools.zip https://dl.google.com/android/repository/platform-tools-latest-linux.zip
unzip -q platform-tools.zip

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

maybe we can add a step to clear the zip file after extracting

Suggested change
rm platform-tools.zip

Comment on lines 45 to 46
# Add adb to PATH for the rest of this workflow
echo "$HOME/platform-tools/platform-tools" >> "$GITHUB_PATH"
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

i am not sure about this working for the rest of the workflow i would exoect it to look like

          export PATH="$HOME/platform-tools/platform-tools:$PATH"

but not 100% sure about it

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

or you can just leave it as it is and check the adb version in th next step

@github-actions
Copy link
Contributor

github-actions bot commented Feb 6, 2026

@emmaoke-w looks like you are rolling back kalium to a previous commitish.

This means that the PR's target branch (develop) is using a newer version of Kalium, and the changes in this PR will rollback Kalium to an older version.

develop This PR
0ac7c385b7dbbf9334125ff4eae9636d212134ad ae71a9a75ae63027c8970905ef5bdeabc59fee8b

Is this intentional?

@github-actions
Copy link
Contributor

github-actions bot commented Feb 6, 2026

@emmaoke-w looks like you are rolling back kalium to a previous commitish.

This means that the PR's target branch (develop) is using a newer version of Kalium, and the changes in this PR will rollback Kalium to an older version.

develop This PR
0ac7c385b7dbbf9334125ff4eae9636d212134ad ae71a9a75ae63027c8970905ef5bdeabc59fee8b

Is this intentional?

@github-actions
Copy link
Contributor

github-actions bot commented Feb 6, 2026

@emmaoke-w looks like you are rolling back kalium to a previous commitish.

This means that the PR's target branch (develop) is using a newer version of Kalium, and the changes in this PR will rollback Kalium to an older version.

develop This PR
0ac7c385b7dbbf9334125ff4eae9636d212134ad ae71a9a75ae63027c8970905ef5bdeabc59fee8b

Is this intentional?

@sonarqubecloud
Copy link

sonarqubecloud bot commented Feb 6, 2026

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants